Pull request overview

This PR replaces the previous Java log-bridge-agent approach with a Swift “holder” parent process that launches the JVM child, relays stdout/stderr over a Unix domain socket, and reports the JVM exit code back to the launcher.

Changes:

• Added --holder mode in Runner to spawn a child runner process, capture its output, and forward logs/exit status via UDS.
• Updated Launcher to pass --holder/--socket-path/--working-directory arguments instead of injecting -javaagent:...log-bridge-agent.jar.
• Adjusted socket loop behavior to wait for an explicit exit code message (0xFF) before exiting.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 7 comments.

    var lastMessages: [String] = []
    var exitCode: Int32?
    
    while true {
        var buffer: [UInt8] = .init(repeating: 0, count: 16384)
        let bytesRead = read(clientSocket, &buffer, buffer.count)
        if bytesRead > 0 {
            if buffer[0] <= 1 {
                if let message: String = .init(bytes: buffer[1..<bytesRead], encoding: .utf8) {
                    if lastMessages.count >= 10 {
                        lastMessages.removeFirst()
                    }
                    lastMessages.append(message)
                    let stream: UnsafeMutablePointer<FILE> = buffer[0] == 0 ? stdout : stderr
                    fputs(message, stream)
                    fflush(stream)

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.